Authorize.net Integration

Authorize.net is a payment gateway that can help you accept credit card and electronic check payments quickly and affordably. More than 305,000 merchants use Authorize.net for payment processing and online fraud prevention solutions.

NetForum is compatible with the Authorize.net payment system.

Setting Up Authorize.net

In order to use Authorize.net as a payment processor in NetForum , you must first have an active Authorize.net account. Please contact your Abila account representative for more information.

Authorize.net is a payment gateway that can help you accept credit card and electronic check payments quickly and affordably. More than 305,000 merchants use Authorize.net for payment processing and online fraud prevention solutions.

NetForum is compatible with the Authorize.net payment system.

NetForum Tasks

After successfully setting up your Authorize.net account, forward your Authorize.net account information to your Abila Project Manager. Your project manager will ensure that the correct information is loaded on your servers and the Authorize.net integration is configured.

To finish the integration, complete the following additional tasks:

  1. Abila will modify the NetForum setup to ensure the correct connection string for the client account on both your 'live' and 'test' sites. At go-live, Abila will update to ensure the connection string for the live site points to the live Authorize.net account.
  2. Abila will then configure the NetForum system options PaymentAPI_iWeb and PaymentAPI_eWeb to enable Authorize.net to be selected as the payment processor.

Troubleshooting and Testing

If you are having issues testing the integration, make sure you have completed the following steps:

  1. Create a Test account
  2. Pass the Test account API Login ID
  3. Pass the Test account Transaction Key
  4. Optional - Pass the Market Type if you get ERROR: "Transactions of this market type cannot be processed on this system."

Your web.config ECommerceSettings should look something like:

<AuthorizeNet username="98Mcm8J3" password="2nKmG2trL85Ha688" x_market_type="2" url="https://test.authorize.net/gateway/transact.dll" />

Common Errors

Error 13: The merchant login ID or password is invalid or the account is inactive. Please view the Authorize.net Document A415.

Error 87: Transactions of this market type cannot be processed on this system. Please view the Authorize.net Document A597.

Note: The payment processor test page has been removed for sites that have Vantiv, Sage, or Paypal and are running NetForum 2013 or later.

Case Study:

  1. A new account was created to work with NetForum . The attempt to authorize from NetForum using test URL (test.authorize.net) would give the error about Merchant Login ID or password is inactive. The new account was active and was in TEST mode, but the error was shown.
  2. When Authorize.net support team was contacted, they told the client that LIVE URL (secure.authorize.net) should be used for this account. Since the account was in TEST MODE, they told that live credit card transactions would not go through.
  3. When NetForum tried to process the test cc with LIVE URL, following error was shown: (TESTMODE) Valid referenced Transaction ID is required. After investigation, it was found that in TESTMODE, Authorize.net does not keep reference of Pre-Auth and hence the Capture fails with this error.
  4. The solution was to create a new test account with Authorize.net. They try to discourage that if you already have a LIVE account, especially if the LIVE account is in TESTMODE.
  5. After creating TEST account, NetForum TEST site was set up to point to TEST URL and LIVE site was set up to point to LIVE URL. The test CC worked properly with the TEST account.
Tips:
  • The PaymentAPI_iWeb and PaymentAPI_eWeb system options must be modified for this integration.
  • If the payment processor test page is active in your system, then the processor that is tested is determined by the system option PaymentAPI_iWeb, which should match the setting for eWeb and the PaymentAPI_eWeb system option. The page will also compare the payment processor configuration to other application configuration files and report any differences. The default setting is PayFlowPro.